ghidra: initial capa explorer extension MVP by vaishakh787 · Pull Request #2839 · mandiant/capa

vaishakh787 · 2026-01-26T09:05:55Z

ghidra: Implement a capa explorer plugin as a Ghidra extension #1980

Summary

Hey @mike-hunhoff , This PR introduces an initial MVP implementation of a capa explorer Ghidra extension.

The purpose of this draft PR is to validate the overall architecture and
integration approach before implementing full capa analysis functionality.

This work aims to replace the current script-based Ghidra workflow with a
proper, installable Ghidra extension that mirrors the IDA Pro capa explorer
plugin experience.

Current functionality

Ghidra extension packaged using the standard Ghidra extension mechanism
Java Swing–based UI integration (no PyQt)
Menu action: Tools ->Run capa analysis
Plugin lifecycle and registration validated
Java -> Python execution bridge implemented
Extension data directory handling verified
Minimal Python entry point for execution testing

This MVP confirms that the extension:

installs cleanly
enables correctly via Ghidra’s plugin manager
executes code from the UI
provides a stable foundation for further development

Non-goals for this PR

This PR intentionally does not implement:

Full capa rule execution
Feature extractor integration
Rule management or selection UI
Result tree view
Program navigation, bookmarks, or highlighting
Full parity with the IDA capa explorer plugin

These will be implemented incrementally after architectural review.

Design notes

UI is implemented entirely in Java Swing, consistent with Ghidra plugin requirements
Python is used only for capa execution logic
No PyQt usage (Ghidra main-thread constraint)
Architecture mirrors the IDA explorer separation of concerns:
- Java: UI and Ghidra integration
- Python: capa execution and result processing
Extension is implemented alongside the existing script-based integration
without breaking backward compatibility

Repository layout

capa/ghidra/
├── helpers.py
├── plugin/
│ ├── capa_explorer.py # existing script integration
│ └── extension/ # new Ghidra extension (this PR)
│ ├── Module.manifest
│ ├── extension.properties
│ ├── build.gradle
│ ├── data/
│ │ └── python/
│ └── src/
│ └── main/java/capa/ghidra/

Related to #1980

google-cla · 2026-01-26T09:06:00Z

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

github-actions

Please add bug fixes, new features, breaking changes and anything else you think is worthwhile mentioning to the master (unreleased) section of CHANGELOG.md. If no CHANGELOG update is needed add the following to the PR description: [x] No CHANGELOG update needed

gemini-code-assist · 2026-01-26T09:06:17Z

Summary of Changes

Hello @vaishakh787, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request lays the foundational architecture for integrating the capa analysis tool directly into Ghidra as a native extension. It transitions the existing script-based workflow into a more robust, installable plugin, providing a dedicated UI component and a menu action to initiate capa analysis. This MVP focuses on establishing the core framework and communication between Ghidra's Java environment and capa's Python logic, setting the stage for comprehensive feature development.

Highlights

Initial MVP for Capa Explorer Extension: This pull request introduces the Minimum Viable Product (MVP) for a capa explorer Ghidra extension, establishing the foundational architecture for integrating capa analysis directly into Ghidra.
Transition from Script-based to Extension-based Workflow: The new implementation moves away from the existing script-based Ghidra workflow, providing a proper, installable Ghidra extension that mirrors the IDA Pro capa explorer plugin experience.
Hybrid Architecture (Java UI, Python Logic): The extension utilizes Java Swing for its user interface and Ghidra integration, while employing a Python execution bridge to handle the core capa analysis logic, ensuring compatibility with Ghidra's main-thread constraints.
New 'Run capa analysis' Menu Action: A new menu action, 'Tools → Run capa analysis', has been added, allowing users to trigger capa analysis directly from the Ghidra UI.
Core Functionality Validation: The MVP successfully validates key functionalities, including clean installation, correct enablement via Ghidra’s plugin manager, and the ability to execute code from the UI, providing a stable base for future development.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	`/gemini review`	Performs a code review for the current pull request in its current state.
Pull Request Summary	`/gemini summary`	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	`/gemini help`	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

gemini-code-assist

Code Review

This pull request introduces a solid MVP for a capa explorer Ghidra extension. The architecture with a Java Swing UI and a Python backend for analysis is a good approach. My review includes suggestions to clean up some boilerplate code, improve error handling and configuration, and some minor code style points. Specifically, I've pointed out unused template files in the capaexplorer package that should be removed, and suggested improvements for handling Python executable paths and exception logging.

capa/ghidra/plugin/extension/src/main/java/capa/ghidra/CapaProvider.java

capa/ghidra/plugin/extension/src/main/java/capa/ghidra/CapaPythonBridge.java

capa/ghidra/plugin/extension/extension.properties

capa/ghidra/plugin/extension/src/main/java/capa/ghidra/CapaPlugin.java

capa/ghidra/plugin/extension/src/main/java/capa/ghidra/CapaProvider.java

capa/ghidra/plugin/extension/src/main/java/capa/ghidra/CapaPythonBridge.java

capa/ghidra/plugin/extension/src/main/java/capaexplorer/CapaExplorerPlugin.java

mike-hunhoff

This seems reasonable so far, but we want to utilize PyGhidra to bridge Java and Python. This implementation creates a separate process to run Python. Additionally, the already analyzed Ghidra database (program object) should be passed to capa for analysis, so the initial binary analysis does not need to be completed twice.

mike-hunhoff · 2026-01-26T16:18:59Z

capa/ghidra/plugin/extension/src/main/java/capa/ghidra/CapaPythonBridge.java

+        Process process =
+            new ProcessBuilder(
+                python,
+                scriptFile.getAbsolutePath()
+            )
+            .redirectErrorStream(true)
+            .start();


PyGhidra should serve as the Python <-> Java bridge. Running Python in a separate process doesn't count 🙂

Thanks for the clarification @mike-hunhoff that makes sense.

You're right: launching Python as a separate process is not the intended model here.
I’ll rework the bridge to use PyGhidra directly for in-process Java ↔ Python execution.

The updated approach will be:

Use PyGhidra as the execution bridge

Pass the already-loaded Program object into Python

Avoid reloading or reanalyzing the binary

Reuse the existing Ghidra analysis database for capa

For this draft PR, my goal was to validate extension packaging and UI wiring.
I’ll update the implementation to follow the PyGhidra-based design next.

Thanks for pointing this out — I’ll push an update shortly.

vaishakh787 · 2026-01-28T21:21:42Z

Hi @mike-hunhoff , I’ve pushed an update to the draft PR addressing your feedback.

The implementation now uses PyGhidra as the Java <-> Python bridge, removes the external Python subprocess, and passes the already-loaded Program object directly into the Python script so the existing analysis database is reused.

Please let me know when you have a chance to take another look, and if anything should be adjusted further.

capa/ghidra/plugin/extension/README.md

capa/ghidra/plugin/extension/.gradle/9.2.0/checksums/checksums.lock

capa/ghidra/plugin/extension/extension.properties

capa/ghidra/plugin/extension/src/main/java/capa/ghidra/CapaPlugin.java

CHANGELOG updated or no update needed, thanks! 😄

vaishakh787 · 2026-02-19T17:31:52Z

Hey @mike-hunhoff , quick update.

I switched execution to GhidraScriptService as suggested and now the full flow works: the script runs in PyGhidra, generates the cache, and the plugin loads it successfully.

Next, I’ll integrate real Capa JSON output and expand the results model/UI.

Let me know if this direction looks good.

mike-hunhoff · 2026-02-19T17:40:41Z

Hey @mike-hunhoff , quick update.

I switched execution to GhidraScriptService as suggested and now the full flow works: the script runs in PyGhidra, generates the cache, and the plugin loads it successfully.

Next, I’ll integrate real Capa JSON output and expand the results model/UI.

Let me know if this direction looks good.

sounds good @vaishakh787 , I look forward to seeing the UI 🙂

vaishakh787 · 2026-02-19T18:42:17Z

Also @mike-hunhoff wanted to contact you regarding GSoC 2026. How do i reach out to you?

mike-hunhoff · 2026-02-19T18:51:14Z

Also @mike-hunhoff wanted to contact you regarding GSoC 2026. How do i reach out to you?

Review https://github.com/mandiant/flare-gsoc - this explains everything about the program, including preferred methods for contacting potential mentors.

github-actions bot previously requested changes Jan 26, 2026

View reviewed changes

gemini-code-assist bot reviewed Jan 26, 2026

View reviewed changes

vaishakh787 marked this pull request as ready for review January 26, 2026 13:16

vaishakh787 marked this pull request as draft January 26, 2026 13:22

vaishakh787 changed the title ~~ghidra: initial capa explorer extension MVP~~ ghidra: initial capa explorer extension MVP Jan 26, 2026

mike-hunhoff reviewed Jan 26, 2026

View reviewed changes

mike-hunhoff requested changes Jan 28, 2026

View reviewed changes

vaishakh787 added 5 commits February 19, 2026 21:10

ghidra: initial capa explorer extension MVP

c09bdc5

ghidra: cleanup extension MVP and address review feedback

cce1eb3

added new line in the end

237fe3f

ghidra: initial capa explorer extension using PyGhidra bridge

17e6e9f

resolving author, README.md, .gitignore

c93b7db

vaishakh787 force-pushed the ghidra-capa-explorer-mvp branch from 8a974a8 to c93b7db Compare February 19, 2026 15:40

vaishakh787 requested a review from mike-hunhoff February 19, 2026 15:41

vaishakh787 added 2 commits February 19, 2026 21:27

chore: ignore gradle cache and build artifacts

c2aa30b

chore: ignore Gradle build artifacts

531853b

vaishakh787 marked this pull request as ready for review February 19, 2026 16:25

vaishakh787 marked this pull request as draft February 19, 2026 16:25

changelog: add entry for ghidra capa explorer MVP

d0f2339

small changes to comments

fd7e792

vaishakh787 added 4 commits February 19, 2026 23:15

author modified

355a179

author modified

682be13

added new lines

444ebb3

minor changes

32a754d

Merge branch 'mandiant:master' into ghidra-capa-explorer-mvp

7a5a4bd

Conversation

vaishakh787 commented Jan 26, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Current functionality

Non-goals for this PR

Design notes

Repository layout

Uh oh!

google-cla bot commented Jan 26, 2026

Uh oh!

github-actions bot left a comment

Choose a reason for hiding this comment

Uh oh!

gemini-code-assist bot commented Jan 26, 2026

Summary of Changes

Highlights

Footnotes

Uh oh!

gemini-code-assist bot left a comment

Choose a reason for hiding this comment

Code Review

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

mike-hunhoff left a comment

Choose a reason for hiding this comment

Uh oh!

mike-hunhoff Jan 26, 2026

Choose a reason for hiding this comment

Uh oh!

vaishakh787 Jan 26, 2026

Choose a reason for hiding this comment

Uh oh!

vaishakh787 commented Jan 28, 2026

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

vaishakh787 commented Feb 19, 2026

Uh oh!

mike-hunhoff commented Feb 19, 2026

Uh oh!

vaishakh787 commented Feb 19, 2026

Uh oh!

mike-hunhoff commented Feb 19, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

vaishakh787 commented Jan 26, 2026 •

edited

Loading